                                    FYI
(Note:  The origin of this information may be internal or
external to Novell.  Novell makes every effort within its means
to verify this information.  However, the information provided in
this document is FOR YOUR INFORMATION only.  Novell makes no
explicit or implied claims as to the validity of this
information.)

          TITLE:  EXEPACKED AND COMPRESSED EXECUTABLES
   DOCUMENT ID#:  FYI-M-1304
           DATE:  06MAY93
        PRODUCT:  DR DOS
PRODUCT VERSION:  6.0
     SUPERSEDES:  N/A

        SYMPTOM:  PACKED FILE CORRUPT MESSAGE OR NOT ENOUGH
MEMORY

  ISSUE/PROBLEM:  Executing some exepacked or compressed
executables produces the error message:  Packed File corrupt.

Relocating the DOS kernel can free up additional Conventional
Memory.   In many cases relocating the kernel provides more than
575K Available Conventional.

Certain exepacked or compressed executables may not execute when
there is more than 575k of Available Conventional Memory.  This
situation can produce a Packed File Corrupt Error Message.

All DR DOS versions from 5.0 through 6.0 (4/92) automatically pad
the first 64k of Conventional Memory when the operating system
detects that these types of executables are loading.  By padding
the Lower 64K these types of software would detect that the Low
Memory area was occupied and they would therefore execute
successfully.

Many newer exepacked and compressed executables are written to
take advantage of the extra free memory available when the DOS
Kernel is relocated.  These types of executables typically
require more than 575k free Conventional Memory to run.  Padding
the first 64k of memory would therefore prevent the program from
running.

Patch 326 and UPD393 do not pad the Lower 64K of Conventional
when an exepacked or compressed executable runs.  This change
allows the newer executables to load.

When an older exepacked or compressed executable runs on a DR DOS
machine with system files from Patch 326 or UPD393 a PACKED FILE
CORRUPT error will be generated.

       SOLUTION:  Use MEMMAX to prevent the PACKED FILE CORRUPT
error when running an older executable on a machine with Patch
326 or 3/93 (UPD393) file dates.  MEMMAX -L will pad Lower Memory
before executing the file.   When you've finished using the
executable use MEMMAX + L to unpad Lower Memory.  This can be
done at the command line.  However, writing a batch file may be
more efficient.

     MEMMAX -L           (This pads Lower Memory)
     CD\DIRECTORY NAME
     EXECUTABLE
     MEMMAX +L           (This restores Lower Memory)

NOTE:     MEMMAX cannot be run from a shell but only from the
first copy of COMMAND.COM.
ЩЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭбЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭбЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЛ
К EXECUTABLE          Г   DR DOS           Г  DR DOS PATCH 326   К
К                     Г   4/92 & OLDER     Г  or 3/93 FILE DATES К
К                     Г   FILE DATES       Г                     К
ЬЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭиЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭиЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЙ
К Older exepacked &   Г   Run Fine         Г  May receive PACKED К
К compressed          Г                    Г  FILE CORRUPT error К
К executables         Г                    Г  See *              К
ЧФФФФФФФФФФФФФФФФФФФФФХФФФФФФФФФФФФФФФФФФФФХФФФФФФФФФФФФФФФФФФФФФЖ
К Newer exepacked &   Г Not enough Memory  Г  Run Fine           К
К compressed          Г to run even though Г                     К
К executables         Г the MEM report     Г                     К
К                     Г shows sufficient   Г                     К
К                     Г available          Г                     К
К                     Г Conventional       Г                     К
К                     Г See **             Г                     К
ШЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЯЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЯЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭЭМ

* Use MEMMAX to pad Lower Memory or contact the maker of the
executable for an update.

** Update with Patch 326 or UPD393.